-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
r/aws_elasticache_cluster: fix transit_encryption_enabled for redis #33451
Conversation
Community NoteVoting for Prioritization
For Submitters
|
- Removes the default `false` value and makes the argument optional and computed. For `redis` engine types the value will effectively always be computed. - Removes the `CustomizeDiff` function focused on the `transit_encryption_enabled` attribute, instead relying on the native AWS errors to provide the same feedback. 1. AWS error for minimum supported memcached version check: ``` Error: creating ElastiCache Cache Cluster (jb-test-memcached): InvalidParameterCombination: Encryption features are not supported for engine version 1.6.6. Please use engine version 1.6.12 ``` 2. AWS error when attempting to create a `redis` cluster with `transit_encryption_enabled` set (must be set on replication group instead): ``` Error: creating ElastiCache Cache Cluster (jb-test-redis): InvalidParameterCombination: Encryption feature is not supported for engine REDIS. ```
1825662
to
17138db
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀.
% make testacc TESTARGS='-run=TestAccElastiCacheCluster_ReplicationGroupID_transitEncryption' PKG=elasticache ACCTEST_PARALLELISM=2
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/elasticache/... -v -count 1 -parallel 2 -run=TestAccElastiCacheCluster_ReplicationGroupID_transitEncryption -timeout 180m
=== RUN TestAccElastiCacheCluster_ReplicationGroupID_transitEncryption
=== PAUSE TestAccElastiCacheCluster_ReplicationGroupID_transitEncryption
=== CONT TestAccElastiCacheCluster_ReplicationGroupID_transitEncryption
--- PASS: TestAccElastiCacheCluster_ReplicationGroupID_transitEncryption (1528.68s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/elasticache 1534.081s
This functionality has been released in v5.17.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
Fixes a regression for
redis
engine types caused by the newtransit_encryption_enabled
argument (added in v5.16.0).false
value and makes the argument optional and computed. Forredis
engine types the value will effectively always be computed.CustomizeDiff
function focused on thetransit_encryption_enabled
attribute, instead relying on the native AWS errors to provide the same feedback.redis
cluster withtransit_encryption_enabled
set (must be set on a replication group instead)Before:
After:
Relations
Closes #33403
Relates #26987
References
Output from Acceptance Testing